bootstrap-fix-include-next
authorLLVM Packaging Team <pkg-llvm-team@lists.alioth.debian.org>
Sat, 5 Nov 2022 08:14:23 +0000 (08:14 +0000)
committerSylvestre Ledru <sylvestre@debian.org>
Sat, 5 Nov 2022 08:14:23 +0000 (08:14 +0000)
commit84853037081b350409241c480eda389b77eb3142
treed279f56c1243e50505a647d402a69aca23cc280d
parent36921c326f6661c27dc5905ba43b670b7f10f584
bootstrap-fix-include-next

When doing a bootstrap, we use a newly built clang.
When this one is used, if already installed on the system,
we have clang header in two places:
llvm-toolchain-7-7/build-llvm/lib/clang/7.0.0/include/inttypes.h
and
/usr/include/clang/7.0.0/include/inttypes.h

Because clang expects only one of his headers to be available, it uses
include_next to get the glibc (libc6-dev package) header.

However, in the previous example, because we have inttypes.h twice in the
include search path, clang's header will call itself without any effect.
Therefore, it will do include_next until the define from the libc is existing (ex: _INTTYPES_H)

Gbp-Pq: Name bootstrap-fix-include-next.diff
clang/lib/Headers/inttypes.h
clang/lib/Headers/limits.h